Filtering User Interface for a Data Summary Table

ABSTRACT

A graphical user interface for creating a data summary table includes a data summary table including a plurality of fields, and a filtering pane programmed to apply filters to items in the fields of the data summary table, the filtering pane including a field selector control, wherein the field selector control is programmed to allow for selection of a field of the fields in the data summary table to define filtering for the field.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/311,736, filed Dec. 6, 2011, entitled “Filtering User Interface for aData Summary Table,” and assigned U.S. Pat. No. 9,223,772, which is acontinuation of U.S. patent application Ser. No. 11/223,631, filed Sep.9, 2005, entitled “Filtering User Interface for a Data Summary Table,”and now U.S. Pat. No. 8,095,866, which application is also related toU.S. patent application Ser. No. 11/222,660, filed Sep. 9, 2005,entitled “Automated Placement of Fields in a Data Summary Table,” andnow U.S. Pat. No. 7,480,675 and U.S. patent application Ser. No.11/223,527, filed Sep. 9, 2005, entitled “User Interface for Creating aSpreadsheet Data Summary Table,” and now U.S. Pat. No. 8,601,383, theentireties of which are hereby incorporated by reference.

BACKGROUND

Data summary tables can be used to analyze large amounts of data. Oneexample of a data summary table is PIVOTTABLE dynamic views that can begenerated using Microsoft Corporation's EXCEL spreadsheet software. Adata summary table provides an efficient way to display and summarizedata that is supplied by a database program or that is in a data listingof a spreadsheet. A user can select fields of the data to include withinpage, row, column, or data regions of the data summary table and canchoose parameters such as the sum, variance, count, and standarddeviation to be displayed for selected data fields. Data in a databasethat can be queried from within a spreadsheet program, or spreadsheetdata including lists, can be analyzed in a data summary table.

Although a data summary table is designed so that data can beefficiently and intuitively analyzed, creation of the data summary tableitself can be challenging for novice users. For example, some programsprovide wizards that assist the user in creating a data summary table.While these wizards may be helpful in creating an initial data summarytable, the wizards cannot easily be used to modify the display once itis created. Other programs allow users to drag and drop desired fieldsdirectly onto the data summary table. While these programs provide theuser with greater flexibility when creating the display, such programscan be less intuitive for a novice to use.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

According to one aspect, a graphical user interface for creating a datasummary table includes a data summary table including a plurality offields, and a filtering pane programmed to apply filters to items in thefields of the data summary table, the filtering pane including a fieldselector control, wherein the field selector control is programmed toallow for selection of a field of the fields in the data summary tableto define filtering for the field.

According to another aspect, in a computer system having a graphicaluser interface for a data summary table, a method includes: allowingselection of a field from a plurality of fields; presenting filteringoptions for the field; associating selected filtering with the field;and thereafter, applying the selected filtering to items in the fieldwhen the field is added to a data summary table.

According to another aspect, a computer-readable medium hascomputer-executable instructions for performing steps including:allowing selection of a field from a plurality of fields; presentingfiltering options for the field; associating selected filtering with thefield; and thereafter, applying the selected filtering to items in thefield when the field is added to a data summary table.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 illustrates an example general purpose computing system;

FIG. 2 illustrates an example sheet of a spreadsheet program;

FIG. 3 illustrates an example data summary table and task pane of thespreadsheet program;

FIG. 4 illustrates the example task pane of FIG. 3;

FIG. 5 illustrates another example task pane;

FIG. 6 illustrates an example menu for replacement of a field in alayout pane of a task pane;

FIG. 7 illustrates an example method for placement of a field in alayout pane of the task pane of FIG. 4;

FIG. 8 illustrates the example data summary table and task pane of FIG.3 with a field added to the table;

FIG. 9 illustrates the example data summary table and task pane of FIG.3 with multiple fields added to the table;

FIG. 10 illustrates the example data summary table and task pane of FIG.9 with a field rearranged on the table;

FIG. 11 illustrates another example task pane;

FIG. 12 illustrates an example menu for modifying a layout of the taskpane of FIG. 11;

FIG. 13 illustrates the example task pane of FIG. 11 in a differentlayout;

FIG. 14 illustrates the example task pane of FIG. 11 in a differentlayout;

FIG. 15 illustrates the example task pane of FIG. 11 in a differentlayout;

FIG. 16 illustrates the example task pane of FIG. 11 in a differentlayout;

FIG. 17 illustrates an example method for placement of a field in alayout pane of the task pane of FIG. 4;

FIG. 18 illustrates another example method for placement of a field in alayout pane of the task pane of FIG. 4;

FIG. 19 illustrates another example method for placement of a field in alayout pane of the task pane of FIG. 4;

FIG. 20 illustrates an example filtering task pane;

FIG. 21 illustrates an example manual filter area for another filteringtask pane;

FIG. 22 illustrates an example fly-out menu for the filtering task paneof FIG. 20;

FIG. 23 illustrates another example fly-out menu for the filtering taskpane of FIG. 20;

FIG. 24 illustrates an example dialog box for the filtering task pane ofFIG. 20;

FIG. 25 illustrates another example filtering task pane;

FIG. 26 illustrates an example fly-out menu for the filtering task paneof FIG. 25;

FIG. 27 illustrates another example task pane;

FIG. 28 illustrates an example tool-tip for the task pane of FIG. 27.

DETAILED DESCRIPTION

Embodiments will now be described more fully hereinafter with referenceto the accompanying drawings. Embodiments disclosed herein are examplesand should not be construed as limiting; rather, these embodiments areprovided so that this disclosure will be thorough and complete. Likenumbers refer to like elements throughout.

Embodiments described herein relate to data summary tables used toanalyze data on a computer system.

Referring now to FIG. 1, an example computer system 100 is illustrated.The computer system 100 illustrated in FIG. 1 can take a variety offorms such as, for example, a desktop computer, a laptop computer, and ahand-held computer. In addition, although computer system 100 isillustrated, the systems and methods disclosed herein can be implementedin various alternative computer systems as well.

The system 100 includes a processor unit 102, a system memory 104, and asystem bus 106 that couples various system components including thesystem memory 104 to the processor unit 102. The system bus 106 can beany of several types of bus structures including a memory bus, aperipheral bus and a local bus using any of a variety of busarchitectures. The system memory includes read only memory (ROM) 108 andrandom access memory (RAM) 110. A basic input/output system 112 (BIOS),which contains basic routines that help transfer information betweenelements within the computer system 100, is stored in ROM 108.

The computer system 100 further includes a hard disk drive 112 forreading from and writing to a hard disk, a magnetic disk drive 114 forreading from or writing to a removable magnetic disk 116, and an opticaldisk drive 118 for reading from or writing to a removable optical disk119 such as a CD ROM, DVD, or other optical media. The hard disk drive112, magnetic disk drive 114, and optical disk drive 118 are connectedto the system bus 106 by a hard disk drive interface 120, a magneticdisk drive interface 122, and an optical drive interface 124,respectively. The drives and their associated computer-readable mediaprovide nonvolatile storage of computer readable instructions, datastructures, programs, and other data for the computer system 100.

Although the example environment described herein can employ a hard disk112, a removable magnetic disk 116, and a removable optical disk 119,other types of computer-readable media capable of storing data can beused in the example system 100. Examples of these other types ofcomputer-readable mediums that can be used in the example operatingenvironment include magnetic cassettes, flash memory cards, digitalvideo disks, Bernoulli cartridges, random access memories (RAMs), andread only memories (ROMs).

A number of program modules can be stored on the hard disk 112, magneticdisk 116, optical disk 119, ROM 108, or RAM 110, including an operatingsystem 126, one or more application programs 128, other program modules130, and program data 132.

A user may enter commands and information into the computer system 100through input devices such as, for example, a keyboard 134, mouse 136,or other pointing device. Examples of other input devices include atoolbar, menu, touch screen, microphone, joystick, game pad, pen,satellite dish, and scanner. These and other input devices are oftenconnected to the processing unit 102 through a serial port interface 140that is coupled to the system bus 106. Nevertheless, these input devicesalso may be connected by other interfaces, such as a parallel port, gameport, or a universal serial bus (USB). An LCD display 142 or other typeof display device is also connected to the system bus 106 via aninterface, such as a video adapter 144. In addition to the display 142,computer systems can typically include other peripheral output devices(not shown), such as speakers and printers.

The computer system 100 may operate in a networked environment usinglogical connections to one or more remote computers, such as a remotecomputer 146. The remote computer 146 may be a computer system, aserver, a router, a network PC, a peer device or other common networknode, and typically includes many or all of the elements described aboverelative to the computer system 100. The network connections include alocal area network (LAN) 148 and a wide area network (WAN) 150. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets, and the Internet.

When used in a LAN networking environment, the computer system 100 isconnected to the local network 148 through a network interface oradapter 152. When used in a WAN networking environment, the computersystem 100 typically includes a modem 154 or other means forestablishing communications over the wide area network 150, such as theInternet. The modem 154, which can be internal or external, is connectedto the system bus 106 via the serial port interface 140. In a networkedenvironment, program modules depicted relative to the computer system100, or portions thereof, may be stored in the remote memory storagedevice. It will be appreciated that the network connections shown areexamples and other means of establishing a communications link betweenthe computers may be used.

The embodiments described herein can be implemented as logicaloperations in a computing system. The logical operations can beimplemented (1) as a sequence of computer implemented steps or programmodules running on a computer system and (2) as interconnected logic orhardware modules running within the computing system. Thisimplementation is a matter of choice dependent on the performancerequirements of the specific computing system. Accordingly, the logicaloperations making up the embodiments described herein are referred to asoperations, steps, or modules. It will be recognized by one of ordinaryskill in the art that these operations, steps, and modules may beimplemented in software, in firmware, in special purpose digital logic,and any combination thereof without deviating from the spirit and scopeof the present invention as recited within the claims attached hereto.This software, firmware, or similar sequence of computer instructionsmay be encoded and stored upon computer readable storage medium and mayalso be encoded within a carrier-wave signal for transmission betweencomputing devices.

Referring now to FIG. 2, an example program 200 is shown. In oneexample, program 200 is Microsoft's EXCEL spreadsheet software programrunning on a computer system, such as computer system 100 describedabove. Program 200 includes a spreadsheet 205 with an example list ofdata 210. A user can create a data summary table from data 210.

For example, referring now to FIG. 3, an example user interface 302 ofprogram 200 is shown. User interface 302 includes an initial datasummary table 320 (data summary table 320 is blank in FIG. 3). Datasummary table 320 can be created from data from various sources. In oneexample as shown in FIG. 3, data summary table 320 can be created fromdata from one or more databases, as described further below. In otherembodiments, data summary table 320 can be created from data in aspreadsheet, such as data 210 shown in FIG. 2.

User interface 302 of program 200 also includes an example task pane 450that can be used to create and modify data summary table 320. Forexample, task pane 450 includes a list of the fields from data 210. Theuser can select and deselect fields from task pane 450 to create datasummary table 320, as described further below.

I. Task Pane

Referring now to FIG. 4, example task pane 450 is shown. Task pane 450generally includes a field pane 452 and a layout pane 454. Task pane 450is used to create and modify data summary table 320, as describedfurther below.

Field pane 452 includes a list 453 of each field in a given database orspreadsheet (e.g., spreadsheet 205 as shown in FIG. 2 above). A scrollbar 451 is provided because the list 453 of fields is longer than thespace provided by field pane 452. In some embodiments, field pane 452(and layout pane 454 as well) can be resized by the user. Each field inlist 453 includes a checkbox next to the field. For example, the field“Profit” includes a checkbox 460 positioned adjacent to the fieldcaption. When a field in list 453 is added to layout pane 454 asdescribed below, the checkbox associated with the field is checked. Forexample, checkbox 460 for the “Profit” field is checked because it hasbeen added to layout pane 454.

Layout pane 454 includes a plurality of zones that represent aspects ofthe data summary table 320 that is created using task pane 450. Forexample, layout pane 454 includes a row zone 455, a column zone 456, avalue zone 457, and a filter zone 458. Row zone 455 defines the rowlabels for the resulting data summary table 320. Column zone 456 definesthe column labels for data summary table 320. Value zone 457 identifiesthe data that is summarized (e.g., aggregation, variation, etc.) on datasummary table 320. Filter zone 458 allows for the selection of filteringthat is applied to all other fields in the other zones 455, 456, 457(e.g., a field can be placed in filter zone 458 and one or more itemsassociated with the field can be selected to create a filter to showonly those items for all other fields in layout pane 454 that areassociated with the item(s) selected for the field in filter zone 458).

One or more of the fields from field pane 452 are added to one or moreof the zones of layout pane 454 to create and modify data summary table320. In the example shown, the user can click, drag, and drop a fieldfrom list 453 of field pane 452 to one of the zones of layout pane 454to add a field to the data summary table 320.

For example, as shown in FIG. 5, the user can hover over a particularfield included in field pane 452, such as the “Store Sales” field 466.As the user hovers over the field, the user is presented with across-hair cursor 472 that indicates that the user can click and dragthe selected field from the field pane 452 to one of the zones of thelayout pane 454. Once the user selects the field, the cross-hair cursor472 returns to a normal cursor, and the “Store Sales” field 466 can bedragged and dropped into the value zone 457, as shown. A field cansimilarly be removed from layout pane 454 by selecting and dragging thefield out of layout pane 454.

In another example, the user can check the checkbox associated with aparticular field in field pane 452 to add the field to layout pane 454.For example, if the user selects checkbox 460 associated with the“Profit” field shown in task pane 450 of FIG. 4, this field can be addedto value zone 457 as “Profit” field 462. As described further below,program 200 can be programmed to analyze and place the selected field inan appropriate zone of layout pane 454. The user can similarly unselecta checked field to remove the field from layout pane 454. For example,if the user unselects checkbox 460, the “Profit” field 462 is removedfrom layout pane 454.

In an optional example, if a user clicks on a given field to select thefield without dragging the field to one of the zones of drop zone 454,the user can be presented with a menu (e.g., similar to that of menu 482shown in FIG. 6) that allows the user to select which zone to place thefield.

Referring now to FIG. 7, an example method 500 for adding a field fromfield pane 452 to a zone of layout pane 454 is shown. At operation 501,the user selects a field listed in field pane 452 to add to layout pane454. At operation 502, a determination is made regarding whether theuser selected the checkbox associated with the particular field. If theuser selected the checkbox, control is passed to operation 503, andprogram 200 can automatically determine which zone of layout pane 454 toplace the selected field. Next, in operation 507, the field is added tothe appropriate zone of layout pane 454.

If a determination is made at operation 502 that the user has notselected the checkbox, control is passed to operation 504. At operation504, a determination is made regarding whether the user has selected,dragged, and dropped the field into one of the zones of layout pane 454.If the user has dropped the field into one of the zones of layout pane454, control is passed to operation 507, and the field is added to thezone.

If a determination is made at operation 504 that the user has notdragged and dropped the field, in an optional embodiment control ispassed to operation 505 because the user has selected the field withoutselecting the checkbox or dragging/dropping the field into a zone of thelayout pane 454. At operation 505, program 200 presents the user with amenu to allow the user to select the zone to which to add the field.Next, at operation 506, the user selects the desired zone. At operation507, the field is added to the zone.

Once the field has been added to the zone of layout pane 454, control ispassed to operation 509, and program 200 updates the data summary table320 accordingly, as described below.

Referring again to FIG. 4, once a field such as the “Profit” field fromthe field pane 452 is added to one of the zones of layout pane 454, thecheckbox (e.g., checkbox 460) associated with that field in field pane452 is checked to indicate that the field is part of data summary table320. In addition, the font of the field label associated with the fieldin field pane 452 is bolded. Similarly, when a field has not yet beenmade part of data summary table 320 (or has been removed therefrom), thecheckbox associated with the field is left unchecked and the field isshown in normal, rather than bold, font. Others methods for indicatingthe fields that are part of data summary table 320 can also be used.

As fields are added and removed from layout pane 454 of task pane 450,the resulting data summary table 320 is modified accordingly. Forexample, the user is initially presented with task pane 450 includingfield pane 452 as shown in FIG. 3. Referring to FIG. 8, when the useradds the “Profit” field to value zone 457 of layout pane 454, a sum ofthe data associated with the “Profit” field is automatically added todata summary table 320. Referring to FIG. 9, the user can add additionalfields (e.g., “Sales Average,” “Customers,” “Gender”) to zones of layoutpane 454, and data summary table 320 is updated to include data relatedto the added fields.

Referring to FIG. 10, the user can also move fields from one zone toanother zone in layout pane 454 of task pane 450, and data summary table320 is updated accordingly. For example, the user can move the “Gender”field from column zone 456 to row zone 455, and data summary table 320is automatically updated accordingly to reflect the change. The user canalso move fields within a given zone 455, 456, 457, 458 to change theorder in which the fields are displayed in data summary table 320. Forexample, the user can move the “Gender” field above the “Customer” fieldin row zone 455 so that the “Gender” field is shown prior to the“Customer” field in data summary table 320.

Referring now to FIG. 6, in one example if the user clicks and releasesa field such as “Product Categories” field 481 located in layout pane454 without dragging the field, the user is presented with a menu 482that allows the user to manipulate the placement of the field withinlayout pane 454. For example, menu 482 allows the user to change theposition of the field within a given zone (i.e., “Move Up,” “Move Down,”“Move to Beginning,” “Move to End”), move the field between zones (i.e.,“Move to Row Labels,” “Move to Values,” “Move to Column Labels,” “Moveto Report Filter”), and remove the field from layout pane 454 (i.e.,“Remove Field”). Only those options that are available for a particularfield are shown as active choices in menu 482 (e.g., “Move to RowLabels” is shown as inactive in the example because field 481 is alreadyin row zone 455).

Referring again to FIG. 4, task pane 450 also includes a manual updatecheckbox 469. When checkbox 469 is selected, the resulting data summarytable 320 is not automatically updated as fields are added, rearranged,and removed from layout pane 454 of task pane 450. For example, if theuser selects manual update checkbox 469 and then adds a field to rowzone 455 of layout pane 454, data summary table 320 is not automaticallyupdated to reflect the newly added field. Instead, update occurs afterthe user selects a manual update button 471 that becomes active once achange has been made and a manual update can be performed. Manualupdates can be used to increase efficiency when working with largeamounts of data that require significant retrieval and processing timeto create the data summary table 320. In this manner, the desired fieldsand filtering can be selected prior to creation or revision of the datasummary table 320, which occurs upon selection of the manual updatebutton 471, thereby enhancing efficiency.

Referring to FIG. 11, the fields shown in field pane 452 represent datafields of the “online analysis processing” (OLAP) type. (In contrast,the fields shown in field pane 452 in FIG. 5 are of non-OLAP type,sometime referred to as relational fields.) OLAP is a category of toolsthat provides analysis of data stored in a database. OLAP tools allowusers to analyze different dimensions of multidimensional data. OLAPdata fields are arranged in a hierarchical structure with a plurality oflevels. For example, the “Sales Fact 1991” field includes sub-fields“Store Sales,” “Unit Sales,” and “Store Cost.” Sub-fields can beaccessed by clicking on the drill indicator (plus/minus+/−sign) 556 toexpand and collapse the sub-fields. OLAP data can be arranged intodimensions with hierarchies and measures.

In the embodiment shown, each field listed in field pane 452 includes aplurality of components. A field can be highlighted by hovering over orclicking the field. For example, each field, such as the “Product” fieldshown in FIG. 11 includes selection areas 558 and 559 that allow a userto select and drag the field. Each field also includes checkbox 560 thatcan be used to add/remove the field from data summary table 320. Inaddition, each field of OLAP data type can include drill indicator 556that is used to expand and collapse the sub-fields associated with thefield. In addition, each field includes a drop down area 562 used toaccess filtering options, as described further below.

Referring again to FIG. 4, task pane 450 also includes a control 470that allows the user to modify the layout of task pane 450. For example,the user can select control 470 to access a layout menu 572, as shown inFIG. 12. Layout menu 572 is used to arrange panes 452 and 454. Forexample, if the user selects “Fields and Layout stacked” 573 in control470, field pane 452 is positioned above layout pane 454 in task pane 450to form a single integrated pane, as shown in FIG. 4. If the userselects “Fields and Layout side by side” 574 in control 470, field pane452 is positioned along side layout pane 454 in task pane 450 to form asingle integrated pane, as shown in FIG. 13. If the user selects “Fieldsonly” 575 in control 470, field pane 452 is shown in isolation, as shownin FIG. 14. If the user selects “Layout only 2 by 2” 576 in control 470,layout pane 454 is shown in isolation with zones 455, 456, 457, 458arranged in a 2×2 square, as shown in FIG. 15. If the user selects“Layout only 1 by 4” 577 in control 470, layout pane 454 is shown inisolation with zones 455, 456, 457, 458 arranged in a 1×4 square, asshown in FIG. 16.

In the example shown in FIG. 5, the fields in field pane 452 are listedin alphabetical order. For lists including OLAP type data such as thatshown in FIG. 4, the measures are shown first, and the dimensions areshown in alphabetical order thereafter. In the examples shown, thedimension folders are shown in expanded form, with all other fieldsshown in collapsed form. Other configurations can also be used.

II. Automated Placement of a Field in Layout Pane

Referring again to FIG. 4, if a user selects a field by checking thecheckbox associated with the field, program 200 is programmed toautomatically place the selected field in one of the zones of layoutpane 454, as described below.

Generally, fields of a numeric type are added to value zone 457, andfields of a non-numeric type are added to row zone 455 of layout pane454. For example, fields of a numeric type (e.g., monetary salesfigures) are typically aggregated and are therefore placed in value zone457, while fields of a non-numeric type (e.g., product names) aretypically used as row labels and are therefore automatically placed inrow zone 455.

Referring now to FIG. 17, an example method 600 for automatically addinga selected field to one of the zones of layout pane 454 is shown. Atoperation 601, the user selects a field in field pane 452 using, forexample, the checkbox associated with the field. Next, at operation 602,a determination is made regarding whether the field is of a numerictype. If the field is of numeric type, control is passed to operation603, and the field is added to the value zone 457 for aggregation. Ifthe field is determined to not be of numeric type at operation 602,control is passed to operation 604, and the field is added to the rowzone 455.

In some embodiments, a field of numeric type can be further analyzedprior to adding the field to the value zone 457 to determine if adifferent placement in layout pane 454 is more appropriate. For example,a field including a plurality of zip code values is of numeric type, butit is typically desirable to place such a field in row zone 455, ratherthan in value zone 457. For this reason, fields of numeric type arefurther analyzed in some embodiments using data semantics to identifydesired placement in layout pane 454.

In one embodiment, a lookup table, such as example Table 1 below, isused to identify fields of numeric type that are added to row zone 455rather than value zone 457.

TABLE 1 FieldTypeString MinValue MaxValue “zip” “year” “quarter” 1 4“qtr” 1 4 “month” 1 12 “week” 1 52 “day” 1 31 “id” “number” “socialsecurity number” “ssn” “phone number” “date”In Table 1, the column “FieldTypeString” includes text strings that arecompared to the caption for the selected field, as described furtherbelow. In the example shown, the caption for the selected field iscompared against each string in the FieldTypeString column of Table 1 toidentify any case-insensitive matches.

If a match is made between a text string in the FieldTypeString columnand the caption for the selected field, numeric items in the field arefurther analyzed using the values in the “MinValue” and “MaxValue”columns of Table 1. The value in the MinValue column specifies theminimum value of any of the items of the given FieldTypeString type. Thevalue in the MaxValue column specifies the maximum value of any of theitems of the given FieldTypeString type. If no MinValue is defined inTable 1 for a particular FieldTypeString type, a determination is maderegarding whether the numeric items are integers below the MaxValue. Ifno MaxValue is defined for a particular FieldTypeString type, adetermination is made regarding whether the numeric items are integersabove the MinValue. If neither a MinValue nor a MaxValue is defined fora particular FieldTypeString type, a determination is made regardingwhether the numeric items are integers.

For example, if a selected field includes the caption “Month,” Table 1is parsed and a match is identified with FieldTypeString value “month.”Next, the numeric values associated with the field are parsed todetermine if the numeric values fall within the minimum and maximumvalues “1” and “12” (representing January through December). In oneembodiment, all numeric items for the field are tested. In otherembodiments, such as when there are a significantly large number ofnumeric items, only a sample of the numeric items is tested against theminimum and maximum values in Table 1. If all of the values fall withinthe minimum and maximum values, then the field is added to the row zone455, rather than the value zone 457, as described further below.

The text strings and minimum and maximum values shown in Table 1 areexamples only, and different strings and values can be used. Forexample, the text strings and minimum/maximum values can be modifieddepending on the geographic location at which the data is generated(e.g., phone number values can differ depending on geographic location).In other embodiments, different types of semantic checking can be used.For example, the number of digits of the numeric items can be analyzedin addition to or in place of checking the actual values for the numericitems. For example, if a caption for a field matches the text string“zip” (i.e., zip codes), the number of digits for the numeric items inthe field can be examined to see if the digits fall between a minimum offive (e.g., “90210” includes five digits) and a maximum of ten (e.g.,“90210-1052” includes ten digits).

Referring now to FIG. 18, an example method 610 is shown for automaticplacement of a selected field in layout pane 454. Method 610 is similarto method 600 described above, except that fields of numeric type arefurther analyzed. At operation 611, the user selects a field in fieldpane 452 using, for example, the checkbox associated with the field.Next, at operation 612, a determination is made regarding whether thefield is of numeric type. If the field is of non-numeric type, controlis passed to operation 613, and the field is added to row zone 455.

If the determination at operation 612 is that the field is of a numerictype, control is passed to operation 615. At operation 615, the captionfor the field is parsed, and, at operation 616, the caption is comparedto a lookup table of text strings such as that shown in Table 1 above.If a match between the caption and a text string is not made inoperation 616, control is passed to operation 619, and the field isadded to value zone 457. If a match in operation 616 between the captionand a text string in Table 1 is made, control is passed to operation617.

At operation 617, numeric items of the field are parsed, and, atoperation 618, the values of the numeric items are compared to theminimum and maximum values in Table 1 associated with the text string.If the numeric items fall outside the minimum and maximum values asdescribed above, control is passed to operation 619, and the field isadded to value zone 457. If the numeric items fall within the minimumand maximum values at operation 618, control is passed to operation 613,and the field is added to row zone 455.

In this manner, specific fields of numeric type can automatically beidentified and placed in the row zone 455, rather than the default valuezone 457. If a field is automatically placed by program 200 in aparticular zone of layout pane 454 and the user wants the field to beplaced in a different zone, the user can select and drag the field tothe desired zone.

In some embodiments, fields associated with date information areidentified and placed in column zone 456, rather than row zone 455 orvalue zone 457. For example, method 630 shown in FIG. 19 is similar tomethod 610 described above, including operations 61-619. However, atoperation 618, if the numeric items fall within the minimum and maximumvalues, control is passed to operation 631. At operation 631, adetermination is made as to whether the field is a date field. In theexample shown, this determination is made by the text string to whichthe caption is matched. For example, if the caption for the fieldincludes the text “Date” and is matched with the text string “date” inTable 1, then the field is identified as a date field. If the field is adate field, control is passed to operation 632, and the field is addedto column zone 456. If the field is not a date field, control is passedto operation 613, and the field is added to row zone 455.

In alternative embodiments, Meta data associated with a particular fieldcan be used to identify attributes about the field. For example, Metadata can be used to identify if a field is a numeric and/or a datefield.

In some embodiments, the following rules are used when automaticallyadding a field identifying OLAP data to layout pane 454 and data summarytable 320:

A. OLAP Hierarchies/OLAP Named Sets

-   -   1. the hierarchy is added to the row zone    -   2. the hierarchy is nested on the inside of all other fields in        the row zone    -   3. for hierarchies with multiple levels, the highest level field        is displayed in the data summary table and the user can drill to        see lower level fields

B. OLAP Measures/OLAP KPI Expressions

-   -   1. if at least one measure is already added, the measure is        added to the same zone as the already added measures    -   2. adding the second measure introduces a Data field (see, for        example, “Σ Values” field in FIG. 10) in the layout pane, and        the Data field is placed in the column zone by default—the Data        field is displayed in the layout zone when there are two or more        fields in the value zone    -   3. when added, the Data field is nested on the inside of all        other fields in the column zone    -   4. the Data field resides in either the row or column zones

In some embodiments, the following additional rules are used whenautomatically adding a field identifying non-OLAP data, or relationalfield, to layout pane 454 and data summary table 320:

A. for non-numeric fields, the field is added to the row zone—the fieldis nested on the inside of all other fields in the row zone

B. for numeric fields, the field is added to the value zone

-   -   1. if at least one field is already in the value zone, this        field will be added to the same zone as the already added field    -   2. adding the first field to the value zone introduces the Data        field in the layout pane, and the Data field is placed in the        column zone by default    -   3. when added, the Data field is nested on the inside of all        other fields in the column zone    -   4. the Data field resides in either the row or column zones

III. Filtering Task Pane

Referring again to FIG. 11, one or more filters can be applied to itemsfor a particular field to limit the information that is included in thedata summary table 320. For example, the user can use drop down area 562for a particular field listed in field pane 452 of task pane 450 toaccess a filtering task pane 700.

Referring now to FIG. 20, example filtering task pane 700 is shown.Interface 700 generally includes a field selector drop down control 705,a manual filter area 707, and a filtering control area 709.

Selector drop down control 705 can be used to select different fieldsfor filtering. For OLAP data, the fields in selector drop down control705 can be displayed in a hierarchical arrangement, and drop downcontrol 705 can be used to select different levels of OLAP data forfiltering. In the example shown, the field selected is the “Country”field.

Manual filter area 707 lists all of the items associated with the fieldshown in selector drop down control 705. Checkboxes are associated witheach item listed in manual filter area 707 to allow the user to manuallyselect which items are included in the filter. Referring to FIG. 21, forOLAP data, sub-items can be accessed by clicking on the drill indicatorplus/minus (+/−) sign to expand and collapse the items associated witheach field listed in manual filter area 707. For example, the “Drink”and “Food” items are shown in expanded form. Checkbox 713 is selectedfor the “Food” item, which results in the selection of each sub-item of“Food” as well. For the “Drink” item, only sub-item “AlcoholicBeverages” is selected, and checkbox 712 associated with the “Drink”item is provided with a mix indicator to show that only a portion ofsub-items of the “Drink” item are selected. A “select all” checkbox 711can be selected to select/deselect every item at all levels shown infilter area 707.

Referring again to FIG. 20, when the user uses selector drop downcontrol 705 to select a different field, manual filter area 707 isupdated accordingly to list the items associated with the field shown inselector drop down control 705. If the newly selected field is fromanother level of the same hierarchy as the originally selected field inselector drop down control 705, manual filter area 707 remains unchangedbecause all levels of items are shown in manual filter area 707 for OLAPdata.

Filtering control area 709 lists the filter controls that are availablefor application to the selected field shown in selector drop downcontrol 705. Controls 710 allow the user to change the order in whichfiltered items are listed. For example, the user can select one ofcontrols 710 to have the filtered items listed in alphabetic order fromA→Z or from Z→A. Control 715 is used to provide additional sortingoptions, such as, for example, sorting by a particular field.

The user can select control 720 to remove all filtering for the field indrop down selector 705. Controls 725 and 730 allow the user to selectparticular filters to apply to the field in drop down selector 705. Forexample, if the user selects control 725, the user is presented with afly-out menu 740, shown in FIG. 22. Menu 740 lists a plurality offilters that can be applied to the selected field. The filters listed inmenu 740 are those filters that are typically applied to label fields.These filters include, without limitation, “Begins With,” “Does NotBegin With,” “Ends With,” “Does Not End With,” “Contains,” and “Does NotContain.” The user can select a filter from menu 740 to apply thatfilter to the items in the field. Likewise, the user can select control730 to access fly-out menu 745, shown in FIG. 23. Menu 745 includesfilters that can be applied to value fields. These filters include,without limitation, “Equals,” “Does Not Equal,” “Greater Than,” “GreaterThan Or Equal To,” “Less Than,” “Less Than Or Equal To,” “Between,” and“Not Between.”

Referring now to FIG. 24, when the user selects a filter from one of thefly-outs 740, 745, the user is presented with a dialog box such asdialog box 760 to build the desired filter. In dialog box 760, a fieldselection box 772 is pre-populated with the with the selected field inselector drop down control 705, and a filter selection box 774 ispre-populated with the filter selected from fly-out 740, 745. The usercan select a different field by selecting the drop down menu in fieldselection box 772 to, for example, access other fields currentlyincluded in value zone 457. The user can select a different filter byselecting the drop down menu in filter selection box 774, which providesa listing of all filters available for the data type. A criteria box 776allows the user to place the value for filtering therein. For example,if the user selects the “Store Sales” item in manual filter area 707 andthen selects the “Greater Than” filter from fly-out 745, dialog box 770is presented to the user. The user can enter the value “50000” incriteria box 776 to set the filter to filter all Store Sales that aregreater than $50,000.

Referring now to FIG. 25, controls 725 and 730 can be modified dependingupon the type of field shown in selector drop down control 705. Forexample, task pane 700 includes a field of the date type and thereforeincludes control 725 that allows for filtering by date, and control 730that allows for filtering by value. The user can select control 725 toaccess fly-out menu 760 shown in FIG. 26. Fly-out menu 760 includes aplurality of filters that can be applied to a field of data type.

In some embodiments, the user is presented with only those controls thatare applicable to a selected field. For example, if the user selects afield of non-date and non-numeric type, control 725 is active to providefly-out menu 740 with filters applicable to such a field. If the userselects a date field, control 725 is active to provide fly-out menu 760with filters applicable to date fields. If the user selects a field ofnumeric, non-date type, control 730 is active to provide fly-out menu745 with filters applicable to numeric data fields.

In some embodiments, filters can be associated with a given field beforethe field is added to the data summary table 320. The filter is actuallyapplied when the particular field is added to the data summary table320. In this manner, the amount of data that is accessed and summarizedon data summary table 320 can be reduced, thereby increasing efficiency.If a filter is applied to a field that is already included in datasummary table 320, data summary table 320 is updated in view of thefilter to show only the filtered items.

Additional details regarding the application of the selected filters tothe data is found in U.S. patent application Ser. No. 11/157,634,Attorney Docket No. 14917.0108US01/311178.01, filed on Jun. 21, 2005 andentitled “Dynamically Filtering Aggregate Reports Based on ValuesResulting from One or More Previously Applied Filters,” the entirety ofwhich is hereby incorporated by reference.

A checkbox indicator 752 (see FIG. 25) in filtering pane 700 is placedadjacent to any filters that have been applied. Referring now to FIG.27, once a filter is applied to a given field, a filter icon 810 isshown adjacent to the field in field pane 452 of task pane 450 toindicate that a filter is applied to the field. In some embodiments, asimilar filter icon is also associated with each filtered field inlayout pane 454 and in data summary table 320.

In addition, when the pointing device hovers over the particular fieldwith filter icon 810, a tool-tip 830 is provided, as shown in FIG. 28.Tool-tip 830 lists the filtered fields in one of three sections, manualfilters, label filters, and value filters. Tool-tip 830 also lists thefiltered fields in the order of evaluation with the type of filterapplied. For filters with longer labels, a portion of the label can betruncated as required to fit within the tool-tip. For each filter,tool-tip 830 shows that a manual filter is first applied to the “Year”field for years 2000, 2001, 2002, 2003, and 2004. Tool-tip 830 indicatesthat a text filter is then applied to the “Product Name” field,requiring the text “ab.” Additional filtering is also shown in tool-tip830. In this manner, the user can identify which filters are applied forthe data summary table 320, and can also identify the order in which thefilters are applied by examining tool-tip 830.

In the example shown, the user can use drop down area 562 (see FIG. 11)for a particular field listed in task pane 450 to access filtering taskpane 700. If the user accesses interface 700 from data summary table320, the default field shown in selector drop down control 705 is thefield that is currently selected in data summary table 320. The user canselect another field using selector drop down control 705. In otherembodiments, filtering task pane 700 can also be accessed from withindata summary table 320 by selecting drop down areas 862 in data summarytable 320. See FIG. 9. In other embodiments, the user can accessfiltering task pane 700 by selecting one or more fields in data summarytable 320 and right-clicking on the selected fields to access one ormore filtering options. These options can include, for example,including or excluding the selected fields in a manual filter, orfiltering the selected fields using the label, date, or value filtersdescribe above.

If filtering task pane 700 is accessed from data summary table 320, thefields listed in drop down control 705 can be selected based on wherethe user accesses interface 700. For example, if the user selects dropdown area 862 from a field in a row of data summary table 320, allfields currently on rows are shown. If the user instead selects dropdown area 862 from a field in a column of data summary table 320, allfields currently on columns are shown.

In the example shown, filtering information is stored with theparticular field to which it is applied. For example, if filtering isapplied to a field that is not part of data summary table 320, thefiltering information is associated with the field and applied when thefield is added to data summary table 320. Likewise, if a field with afilter is removed from data summary table 320, the filter information isretained with the field so that if the field is later added back to datasummary table 320, the filter is reapplied. As noted above, filteringfor a field can be removed by selecting the field and then selectingcontrol 720 (see FIG. 20).

The various embodiments described above are provided by way ofillustration only and should not be construed as limiting. Those skilledin the art will readily recognize various modifications and changes thatmay be made without following the example embodiments and applicationsillustrated and described herein, and without departing from the truespirit and scope of the present invention, which is set forth in thefollowing claims.

The claimed invention is:
 1. A graphical user interface for creating adata summary table, the user interface comprising: a data summary tableincluding a plurality of fields; and a filtering pane programmed toapply filters to items in the fields of the data summary table, thefiltering pane including a field selector control, wherein the fieldselector control is programmed to allow for selection of a field of thefields in the data summary table to define filtering for the field. 2.The user interface of claim 1, wherein the field selector control is adrop down menu programmed to list at least a portion of the fields inthe data summary table.
 3. The user interface of claim 1, wherein thefiltering pane is programmed to modify filtering options presented inthe filtering pane in response to a type of the field selected in thefield selector control.
 4. The user interface of claim 3, wherein thefiltering pane is programmed to include: text filters if the fieldselected in the field selector control is of a non-numeric type; datefilters if the field selected in the field selector control is of a datetype; and numeric filters if the field selected in the field selectorcontrol is of a numeric type.
 5. The user interface of claim 1, whereinthe filtering pane further comprises a manual filtering area programmedto list a plurality of items in the field.
 6. The user interface ofclaim 5, wherein the filtering pane further comprises a plurality ofcheckboxes, one checkbox being associated with each of the items in themanual filtering area, and wherein the user interface is programmed toapply filters to those items for which a checkbox is selected.
 7. In acomputer system having a graphical user interface for a data summarytable, a method comprising: allowing selection of a field from aplurality of fields; presenting filtering options for the field;associating selected filtering with the field; and thereafter, applyingthe selected filtering to items in the field when the field is added toa data summary table.
 8. The method of claim 7, further comprisinglisting the fields in a field pane.
 9. The method of claim 7, furthercomprising: allowing selection of a second field in the data summarytable data display; presenting second filtering options for the secondfield; and applying second filtering to items in the second field in thedata summary table.
 10. The method of claim 7, further comprising:removing the field from the data summary table; thereafter, adding thefield to the data summary table; and applying the selected filtering tothe items in the field when the field is added to the data summarytable.
 11. The method of claim 7, wherein allowing further comprisesproviding a field selector control for selecting the field from theplurality of fields.
 12. The method of claim 7, further comprisingmodifying presentation of the filtering options in response to a type ofthe field.
 13. The method of claim 12, wherein modifying furthercomprises: providing text filters if the field selected in the fieldselector control is of a non-numeric type; providing date filters if thefield selected in the field selector control is of a date type; andproviding numeric filters if the field selected in the field selectorcontrol is of a numeric type.
 14. The method of claim 7, furthercomprising providing a manual filtering area programmed to list aplurality of the items in the field.
 15. A computer-readable mediumhaving computer-executable instructions for performing steps comprising:allowing selection of a field from a plurality of fields; presentingfiltering options for the field; associating selected filtering with thefield; and thereafter, applying the selected filtering to items in thefield when the field is added to a data summary table.
 16. Thecomputer-readable medium of claim 15, further comprising: allowingselection of a second field in the data summary table data display;presenting second filtering options for the second field; and applyingsecond filtering to items in the second field in the data summary table.17. The computer-readable medium of claim 15, wherein allowing furthercomprises providing a field selector control for selecting the fieldfrom the plurality of fields.
 18. The computer-readable medium of claim15, further comprising modifying presentation of the filtering optionsin response to a type of the field.
 19. The computer-readable medium ofclaim 18, wherein modifying further comprises: providing text filters ifthe field selected in the field selector control is of a non-numerictype; providing date filters if the field selected in the field selectorcontrol is of a date type; and providing numeric filters if the fieldselected in the field selector control is of a numeric type.
 20. Thecomputer-readable medium of claim 15, further comprising providing amanual filtering area programmed to list a plurality of the items in thefield.